Methods and apparatus to perform assignments in wireless communications

ABSTRACT

Example methods and apparatus to perform assignments in wireless communications are disclosed. A disclosed example method to receive resource assignments at a mobile station involves receiving an assignment message from a network and identifying radio block periods assigned to the mobile station. At least one of the assigned radio block periods is separated from a next occurring one of the assigned radio block periods by at least one non-assigned radio block period. The example method also involves processing downlink transmissions from the network based on the assigned radio block periods.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to network communications and,more particularly, to methods and apparatus to perform assignments inwireless communications.

BACKGROUND

Mobile communication devices exchange information with mobilecommunication networks by signaling requests to connect with the mobilecommunication networks. Such is the case when placing telephone callsand/or transmitting data using mobile communication devices. In somewireless and mobile communication systems, a mobile communication devicecan establish a data transfer session with a network by signaling itscommunication capabilities to the network and requesting that thenetwork allocate a data channel for use by the mobile communicationdevice to transfer its data to the network. In response, the network mayassign resources to the mobile communication device to perform the datatransfer. In other instances, a network may initialize a downlink datatransfer by assigning downlink resources for use by a destination mobilecommunication device and transmit data to the destination mobilecommunication device on the assigned downlink resources.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example communications network in which the examplemethods and apparatus disclosed herein may be implemented.

FIG. 2 is an example radio block sequence that may be used to implementdownlink radio blocks communicated by a network to a mobile station oruplink radio blocks communicated by a mobile station to a network.

FIG. 3 is an example partial packet assignment arrangement in whichradio blocks are assigned based on radio block periods for use by mobilestations for uplink or downlink radio block communications.

FIG. 4 depicts an example partial timeslot assignment structure that maybe used to indicate which radio block periods include assigned radioblocks (and hence may include allocated radio blocks) for use by mobilestations for uplink or downlink communications.

FIG. 5 depicts a portion of an example packet assignment messagecontaining a one-in-N partial assignment format that may be used toindicate which radio block periods include assigned radio blocks (andhence may include allocated radio blocks) for use by mobile stations foruplink or downlink communications as shown in FIG. 3.

FIG. 6 depicts a portion of another example packet assignment messagecontaining a bitmap assignment format that may be used to indicate whichradio block periods include assigned radio blocks (and hence may includeallocated radio blocks) for use by mobile stations for uplink ordownlink communications as shown in FIG. 3.

FIG. 7 depicts a portion of another example packet assignment messagecontaining an uplink state flag (USF) offset that may be used toindicate how subsequent uplink radio blocks are to be allocated for useby a mobile station.

FIG. 8 depicts an example uplink and downlink radio block transactionbetween an access network interface and a mobile station in connectionwith the USF offset of FIG. 7.

FIG. 9 depicts an example downlink radio block sequence in which USFtransmissions to a mobile station are aligned with downlink radio blockperiods assigned to the same mobile station for receiving data from anetwork.

FIG. 10 depicts a known technique of specifying maximum radio blocktransmissions and/or receptions per radio block period, limiting thequantity of radio blocks that can be received/transmitted per radioblock period by a network for a mobile station.

FIG. 11 depicts an example technique for specifying a maximum allowablecumulative quantity of resources for multiple downlink radio blockperiods.

FIG. 12 depicts an example use of the technique of FIG. 11 to senddownlink data to a mobile station based on a specified maximumcumulative quantity of resources allowable over multiple downlink radioblock periods.

FIG. 13 depicts a portion of an example control message containing apolling field used by a network to poll a mobile station forinformation.

FIG. 14 depicts an example flow diagram representative of computerreadable instructions that may be used to employ a partial assignmentdata structure of FIG. 4 to identify assigned radio block periods.

FIG. 15 depicts an example flow diagram representative of computerreadable instructions that may be used to identify allocated uplinkresources based on an uplink state flag (USF) offset and received USFvalues of FIGS. 7-9.

FIG. 16 depicts an example flow diagram representative of computerreadable instructions that may be used to send data to a mobile stationusing a maximum cumulative quantity of resources allowable over multipledownlink radio blocks.

FIG. 17 depicts an example flow diagram representative of computerreadable instructions that may be used to identify allocated uplinkradio blocks based on the polling request of FIG. 13 received from anetwork.

FIG. 18 depicts another example flow diagram representative of computerreadable instructions that may be used to identify allocated uplinkradio blocks based on the polling request of FIG. 13 received from anetwork.

FIG. 19 depicts an example block diagram of the mobile station of FIGS.1, 5-8, 12, and 13 that can be used to implement the example methods andapparatus disclosed herein.

FIG. 20 depicts an example block diagram of the access network interfaceof FIGS. 1, 5-8, 12, 13, and 22 that can be used to implement theexample methods and apparatus disclosed herein.

FIG. 21 depicts an example temporary block flow (TBF) offset tableshowing assignments of uplink state flag (USF) values and different USFoffsets to multiple TBFs.

FIG. 22 depicts an example allocation of uplink radio blocks between anaccess network interface and one or more mobile stations in connectionwith the USF offset values of FIG. 21.

FIG. 23 depicts an example flow diagram representative of computerreadable instructions that may be used by an access network to sendindications of uplink resource allocations to a mobile station duringassigned downlink radio block periods using the USF values of FIG. 9.

DETAILED DESCRIPTION

Although the following discloses example methods and apparatusincluding, among other components, software executed on hardware, itshould be noted that such methods and apparatus are merely illustrativeand should not be considered as limiting. For example, it iscontemplated that any or all of these hardware and software componentscould be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, while the following describes examplemethods and apparatus, persons having ordinary skill in the art willreadily appreciate that the examples provided are not the only way toimplement such methods and apparatus.

The example methods and apparatus described herein can be used inconnection with mobile stations such as mobile communication devices,mobile computing devices, or any other mobile or non-mobile element,entity, device, or service capable of communicating wirelessly with awireless network. Mobile stations, also referred to as terminals,wireless terminals, or user equipment (UE), may include mobile smartphones (e.g., a BlackBerry® smart phone), wireless personal digitalassistants (PDA), laptop/notebook/netbook computers with wirelessadapters, etc.

Example methods and apparatus described herein can be used to performpartial-timeslot packet assignments in wireless communications for datatransfer sessions between mobile stations and access networks. Examplemethods and apparatus are described herein as being implemented inconnection with General Packet Radio Service (GPRS) or Enhanced GPRS(EGPRS) networks, GSM (Global System for Mobile communications)networks, Enhanced Data Rates for GSM Evolution (EDGE) networks, andother mobile communication networks to implement data transfers betweensuch networks and mobile stations. However, the example methods andapparatus may additionally or alternatively be implemented in connectionwith other types of wireless networks including other types of mobilecommunication networks to implement data transfers.

Example methods and apparatus are described herein in connection withparticular signalling types or message types used by networks to makepartial packet assignments. However, the example methods and apparatusmay be implemented using any other signalling types and message types.

Example methods and apparatus disclosed herein can be used in connectionwith different types of data transfer sessions including, for example,small data transfer (SDT) sessions, machine-to-machine data transfersessions, downlink data transfer sessions, uplink data transfersessions, and/or any other type of data transfer sessions including anycombination thereof. Data transfers enable communicating data betweenmobile stations and networks on an as-needed basis and can be triggeredby different subsystems of a mobile station or a network upon the needto send information from the mobile station to the network or from thenetwork to the mobile station. Information to be communicated may begenerated by the mobile station (e.g., mobile station statusinformation) or may be user-generated information (e.g., messaging,profile changes). Alternatively, the network may generate information orreceive information from another mobile station or communication device(e.g., a computer, a landline telephone, a voicemail system, a pagingsystem, etc.) intended for a destination mobile station. When a datatransfer need arises, a mobile station may request a connection (e.g.,one or more resources for uplink transmission) with a network or anetwork may initiate a connection with a mobile station.

To establish a data transfer session, a network may assign and/orallocate resources (e.g., data channels, timeslots, spreading codes,etc.) to a mobile station (MS) or to a temporary block flow (TBF) (e.g.,a data transfer session) or to a connection or flow or flow context(e.g., a packet flow context) associated with a temporary flow identity(TFI) value (e.g., TFI values associated with a radio link control (RLC)entity when Enhanced Multiplexing for a Single TBF is used) inaccordance with capabilities (e.g., radio access capabilities (RAC)) ofthe mobile station. To ensure that communications between differentmobile stations and a network do not interfere with one another, thenetwork performs scheduling and allocates different resources todifferent mobile stations. In this manner, the mobile stations canconfigure themselves to communicate with the network using theirallocated resources so that they do not interfere with one another.

The methods and apparatus described herein may be used to implementpartial packet assignments that allow a network (NW) to make partial (orfractional) downlink (DL) and/or uplink (UL) resource assignments (e.g.,packet data channel (PDCH) assignments) available for allocating tomobile stations (MSs) for use in exchanging information with thenetwork. An example resource is a PDCH, which is a logical channelassigned by a network for use in communications between mobilestation(s) and the network. A PDCH has multiple resources in the form ofradio blocks (e.g., single-channel radio blocks or PDCH radio blocks) asdescribed in detail below in connection with FIG. 2. In the illustratedexamples described herein, resources (e.g., radio blocks) assigned by anetwork are not necessarily allocated to a mobile station, but thenetwork may allocate such assigned resources at some point to a mobilestation for use in communicating with the network. Thus, an assignmentspecifies particular resources as available for subsequent allocation toa mobile station. A network may allocate the resources (e.g., radioblocks) of a PDCH to one or more mobile stations to enable exchangingdownlink and/or uplink communications between the mobile station(s) andthe network during data transfer sessions (e.g., TBFs). For example,each resource (e.g., radio block) on the PDCH can be separatelyallocated to a different mobile station so that multiple mobile stationscan share the PDCH (without interfering with one another).

Example partial (or fractional) assignments described herein enable anetwork to assign resources (e.g., uplink and/or downlink radio blocks)on a PDCH at different intervals of occurring radio block instances(referred to herein as partial (or fractional) assignments) withoutassigning every single consecutive resource (or radio block instance)available for the PDCH. In this manner, unlike some prior art systems inwhich a network assigns every consecutive radio block instance on a PDCHas available for allocating to mobile stations for uplink/downlinkcommunications and requiring such mobile stations to monitor everyassigned radio block instance (or every radio block instance which mayconvey information regarding the allocation thereof), the partialassignment techniques described herein allow mobile stations to employpower-saving mechanisms by enabling mobile stations to not have tomonitor one or more radio blocks that they would otherwise be requiredto monitor as a requirement of legacy-type assignments. For example,during some radio block periods, the mobile station may not need tomonitor any radio blocks. Thus, the mobile station may reduce batteryconsumption associated with receiving and processing such radio blocks.For example, in some prior art systems in which a network assigns allconsecutive radio blocks (e.g., radio blocks 0-3) on a PDCH as availablefor allocating for transmission to a mobile station, the mobile stationmust decode every downlink radio block (e.g., every downlink radio block0-3) on the PDCH to determine whether it contains information pertainingto it (e.g., based on TFI values in radio block headers). Suchmonitoring may be used by the mobile station to determine whether any ofthe assigned downlink radio blocks (e.g., the assigned downlink radioblocks 0-3) has been allocated to the mobile station to convey downlinkdata intended for the mobile station. Similarly, the mobile station maybe required to monitor radio blocks to determine whether downlink radioblocks contain information allocating to the mobile station a subsequentone or more of the assigned resources (e.g., subsequent uplink radioblocks). The partial assignments described herein enable a network toassign non-consecutive radio blocks such as, for example, radio blocks 0and 2 (but not radio blocks 1 and 3) on a PDCH as available forallocating to a mobile station so that mobile station need only decodeinstances of downlink radio blocks 0 and 2, while using less powerduring intervening radio blocks 1 and 3.

The partial assignment techniques described herein also enable resourceaddress re-use among different mobile stations by configuring a networkto make different partial assignments of resources (e.g., radio blocks)of the same PDCH as available for allocating to different mobilestations. For example, unlike some prior art systems in which a networkassigns all consecutive radio blocks (e.g., radio blocks 0-3) on a PDCHas available for allocating to a mobile station, the partial assignmentsdescribed herein enable a network to assign a set of non-consecutiveradio blocks (e.g., radio blocks 0 and 2) on a PDCH as available forallocating to a first mobile station and assign another set ofnon-consecutive radio blocks (e.g., radio blocks 1 and 3) on the samePDCH as available for allocating to a second mobile station. In thismanner, the same address (corresponding to the same PDCH) is used toallocate resources on the same PDCH to different mobile stations. Insome example implementations, a mobile station 102 ignores data orcontrol blocks (or any non-broadcast information therein) that themobile station 102 may receive or decode that are not received within adownlink partial assignment, independent of the value of any address(e.g., a TFI) in the received radio block. In some exampleimplementations, a mobile station 102 ignores allocation indicators thatthe mobile station 102 may receive or decode that do not allocate aradio block within an uplink partial assignment, independent of thevalue of any uplink allocation indicator in the received radio block.

In some example implementations, before a network makes a partialassignment for a mobile station and/or allocates resources to a mobilestation, the mobile station may communicate its capabilities to thenetwork related to its compatibility with or ability to operate usingparticular types of assignments, partial assignments, and/or resourceallocations. Additionally, the mobile station may communicate to thenetwork its capabilities related to processing capabilities (or other,secondary capabilities) associated with quantities of data that themobile station can transmit or receive and process within one or moreradio block periods. In this manner, the network can determine the typesof partial assignments and/or resource allocations described herein (orlegacy types of assignments and/or allocations) that it can use for themobile station. In addition, the network can determine how much data(e.g., quantities of radio blocks of data) that the network can send tothe mobile station within one or more radio block periods withoutexceeding the data receiving and processing capabilities of the mobilestation.

Turning now to FIG. 1, an example mobile communications network 100 isshown in communication with a mobile station 102. The mobilecommunications network 100 includes an access network 104 and a corenetwork 106. The access network 104 includes an access network interface108 in communication with the mobile station 102 to enable the mobilestation 102 to exchange information with the core network 106. Theaccess network interface 108 can be implemented using a processor-baseddevice or a controller such as, for example, a packet control unit (PCU)for a GSM/EDGE (Enhanced Data rates for GSM Evolution) radio accessnetwork (GERAN), a radio network controller (RNC) for a UMTS radioaccess network (UMTS RAN), or any other type of controller for any othertype of access network. Although not shown, the access network interface108 may be implemented as at least two entities including a basetransceiver station (BTS) (e.g., a BTS 2004 of FIG. 20) (connecteddirectly to an antenna) and a base station controller (BSC) (e.g., a BSC2002 of FIG. 20) (connected to the core network 106 and typicallyincluding the PCU functionality). In some example implementations, suchas in accordance with 3GPP standards, the access network interface 108is implemented as a combination of functionalities in an entity referredto as a base station subsystem (BSS).

The core network 106 can be a GPRS core network or a core network of anyother communication technology type. In the illustrated example, thecore network 106 includes a mobile switching center (MSC) server 110, aserving GPRS support node (SGSN) 112, and a gateway GPRS support node(GGSN) 114. As is known, the SGSN 112 manages subscriber-specific dataduring subscriber sessions and the GGSN 114 establishes and maintainsconnections between the core network 106 and external packet datanetworks 116 (e.g., the Internet, private networks, etc.).

In the illustrated example of FIG. 1, the mobile station 102 canregister with the core network 106 upon discovering the access network104 by performing a registration process using non-access stratumsignaling. After registering with the core network 106, the mobilestation 102 can subsequently, at one or more times while it isregistered, request connections with the access network interface 108 torequest the access network interface 108 to establish data transfersessions between the mobile station 102 and the access network 104. Forexample, as shown in FIG. 1, the mobile station 102 establishes a datatransfer session 120 with the access network 104. Similarly, the accessnetwork 104 may initiate the establishment of the data transfer session120 with the mobile station 102 to, for example, transmit downlink data.The data transfer session 120 can be a small data transfer session, amachine-to-machine data transfer session, a downlink data transfersession, an uplink data transfer session, and/or any other type of datatransfer session including any combination thereof. During a process toestablish the data transfer session 120 or after the data transfersession 120 has been established, the access network 104 sends packetassignment messages to the mobile station 102 to assign downlink radioblock and/or uplink radio block resources that are available forallocation to the mobile station 102 to receive or send data during thedata transfer session 120. The example methods and apparatus describedherein can be used to implement such packet assignment messages suchthat the access network 104 can make partial assignments of resources tothe mobile station 102 to enable better communication efficiency anddecrease power consumption of the mobile station 102 during the datatransfer session 120.

FIG. 2 is an example radio block period sequence 200 during whichdownlink and/or uplink radio blocks may be communicated between theaccess network 108 and the mobile station 102. In the illustratedexample, seven radio blocks (BLOCK 0-BLOCK 6), an idle frame (X), and apacket timing advance control channel (PTCCH) frame (T) are shown in theblock period sequence 200. In the illustrated examples described herein,each radio block of FIG. 2 noted as BLOCK 0-BLOCK 6 is referred to as aradio block period (RBP). The structure of RBP BLOCK 2 is shown indetail as comprising four frames (F0-F3), and the structure of eachframe is shown in detail as having 8 timeslots each, as is known forGSM/GPRS communications.

In the illustrated example, each of the timeslots corresponds to aseparate PDCH. For example, PDCH 7 is noted in FIG. 2 as comprisingtimeslot 7 of each frame (F0-F3). In the illustrated examples describedherein, timeslots corresponding to the same PDCH (e.g., timeslots 7 ofthe PDCH 7) in a radio block period form a radio block for that PDCH.For example, as shown in FIG. 2, a radio block 202 comprises timeslot 7from each of the frames (F0-F3). Thus, an RBP (e.g., any of BLOCK0-BLOCK 6) comprises multiple radio blocks (e.g., 8 radio blocks, eachcorresponding to a respective one of timeslots 0-7), each on arespective PDCH (e.g., PDCH 0-PDCH 7).

In the illustrated examples described herein, a PDCH assignmentcomprises a set of timeslots (e.g., timeslots 7 of frames F0-F3 shown inFIG. 2) on one carrier or on two carriers. For an uplink assignment, theassignment contains the total set of PDCHs (i.e., timeslotnumber-carrier pairs) that may (subject to allocation) be used by amobile station (e.g., the mobile station 102 of FIG. 1) for uplinktransmissions. For a downlink assignment, the assignment contains thetotal set of PDCHs on which a network (e.g., the access network 104 ofFIG. 1) may send data to the mobile station 102. In the exampleimplementations described herein, an assignment message is a messagethat modifies, adds, or reduces the set of resources assigned to amobile station. Examples of assignment messages in GSM/GPRS systems arePACKET TIMESLOT RECONFIGURE messages, PACKET UPLINK ASSIGNMENT messages,PACKET DOWNLINK ASSIGNMENT messages, HANDOVER COMMAND messages, etc.

Also in the illustrated examples described herein, for any given radioblock period (e.g., any of the RBPs (BLOCK 0-BLOCK 6) of FIG. 2)(normally comprising four TDMA frames (e.g., frames F0-F3 of FIG. 2),and each frame comprising 8 timeslots (e.g., timeslots 0-7 of FIG. 2)),a network (e.g., the access network 104 of FIG. 1) dynamically allocatesresources and determines on which downlink timeslots/uplink timeslots amobile station shall receive/transmit data. For example, in FIG. 2, theaccess network 104 may allocate the radio block 202 resource of theassigned PDCH 7 to the mobile station 102. If the radio block 202 is anuplink resource, the mobile station 102 may use the radio block 202 tosend data to the access network 104. If the radio block 202 is adownlink resource, the mobile station 102 may receive data from theaccess network 104 in the radio block 202. Algorithms employed bynetworks for allocating resources (e.g., the radio block 202) may beimplementation dependent, but typically take into account the mobilestations' multislot classes (i.e., the maximum quantity of timeslots (Txand/or Rx timeslots) on which a mobile station can transmit/receive anda “sum” quantity thereof, and the time required to switch betweentransmit and receive modes) and/or radio access capabilities (RAC) ofmobile stations, and typically take account of the amount of data thenetwork expects a mobile station to receive/transmit.

A destination mobile station, flow, packet flow context, or RLC entity(or other entity/connection) chosen by the network for a particulardownlink radio block period may be indicated by a Temporary FlowIdentity (TFI) (e.g., each uplink or downlink Temporary Block Flow (TBF)established for the destination mobile station is assigned a respectiveTFI in an assignment message). In addition, a network may allocateuplink radio blocks to a specific mobile station by using an UplinkState Flag (USF) as described in more detail below.

In the illustrated examples described herein, resource allocations(e.g., allocations of timeslot resources of assigned PDCHs) may be madeusing Basic Transmit Time Interval (BTTI) blocks or Reduced TransmitTime Interval (RTTI) blocks. A BTTI block consists of a timeslot number(e.g., timeslot 7 of FIG. 2) allocated over four consecutive frames(e.g., frames F0-F3 of FIG. 2). For example, the radio block 202 of FIG.2 comprises frame F0, timeslot 7; frame F1, timeslot 7; frame F2,timeslot 7; and frame F3, timeslot 7 to form a BTTI block. In someexample implementations, a frame (e.g., one of the frames F0-F3) isapproximately 5 milliseconds (ms) in duration, such that a BTTI block(e.g., the radio block 202) spans over a 20-ms duration. A BTTI TBF is aTBF which uses BTTI blocks

Unlike a BTTI block (e.g., the radio block 202) which is formed using asingle timeslot from each of four frames, an RTTI block is formed usinga pair of time slots from each of two frames. In example implementationsthat use RTTI blocks, a radio block period contains only two TDMA frames(e.g., F0 and F1) unlike the four TDMA frames (F0-F3) used to form RBPBLOCK 2 for example implementations that use BTTI blocks. As shown inFIG. 2, an RTTI radio block 204 is formed using a pair of timeslots(timeslot 0 and timeslot 1) of a first frame (F0) and a pair oftimeslots (timeslot 0 and timeslot 1) of a next frame (F1). As such, theRTTI radio block 204 has four timeslots and spans over two frames (e.g.,a reduced radio block period comprising frames F0 and F1) or a 10 msduration. Thus, a BTTI block and an RTTI block can carry the same amountof data because they are both formed of four timeslots, but an RTTIblock can convey the same amount of information in half the timerequired by a BTTI block. The example methods and apparatus describedherein may be used to allocate BTTI blocks, RTTI blocks, and/or anycombination thereof.

FIG. 3 is an example partial packet assignment arrangement 300 of theradio block period sequence 200 in which radio blocks are assigned basedon intervals of radio block periods and allocatable for use by themobile station 102 for uplink or downlink radio block communications(e.g., during the data transfer session 120 of FIG. 1). In theillustrated example of FIG. 3, instead of assigning (and, thus, allowingfor possible allocation to) the mobile station 102 a resource (or aradio block) in every one of the radio block periods (BLOCK 0-BLOCK 6),the partial packet assignment arrangement 300 shows a one-in-N partialassignment, in which N is a quantity of radio block periods (e.g., aquantity of the RBPs BLOCK 0-BLOCK 6). In the illustrated example, theradio block period quantity (N) (e.g., a partial assignment interval) isset to three so that the network-assigned resources (that areallocatable to the mobile station) occur every third radio block period,noted as radio block periods 302 a (BLOCK 0), 302 b (BLOCK 3), and 302 c(BLOCK 6). Thus, the quantity of non-assigned radio block periodsoccurring between the assigned radio block periods 302 a (BLOCK 0), 302b (BLOCK 3), and 302 c (BLOCK 6) is two (i.e., non-assigned radio blockperiod(s)=(N−1)).

When implemented in downlink radio block periods, the radio blockperiods 302 a, 302 b, and 302 c may be allocated for the mobile station102 to receive data from the access network 104. In particular, FIG. 3shows PDCH 0 radio blocks 304 a-c, which are particular resources of theradio block periods 302 a-c that are assigned by the access network 104and may be allocated to one or more mobile stations (e.g., the mobilestation 102 of FIG. 1) for use in communicating with the access network104. In the illustrated example, the PDCH 0 radio blocks 304 a-ccorrespond to a packet data channel 0, and each of the PDCH 0 radioblocks 304 a-c is a radio block of the PDCH 0 in a respective one of theradio block periods 302 a-c that are assigned to the mobile station 104.In the illustrated example, each of the radio blocks 304 a-c isseparated from a next occurring one of the radio blocks 304 a-c by twonon-assigned radio block periods (e.g., non-assigned radio block periods308). For example, assigned radio block period 302 a is separated fromthe next occurring assigned radio block period 302 b by radio blockperiods BLOCK 1 and BLOCK 2 shown as the non-assigned radio blockperiods 308. Alternatively, the partial assignment technique of FIG. 3may be implemented by assigning radio block periods to the mobilestation 102 with only one intervening non-assigned radio block period(e.g., in a one-in-two partial assignment) or with more than twointervening non-assigned radio block periods.

Using the partial assignment of FIG. 3 to assign resources at radioblock periods at N=3 radio block period intervals enables correspondingmobile stations to employ power-saving techniques during interveningradio block periods (e.g., BLOCK 1, BLOCK 2, BLOCK 4, and BLOCK 5) nothaving assigned resources allocatable to such mobile stations becausethe mobile stations need not monitor and decode radio blocks duringthose radio block periods.

FIG. 4 depicts an example partial timeslot assignment structure 400 thatmay be used to assign resources (e.g., the radio blocks 304 a-c of FIG.3) within radio block periods (e.g., one or more of the radio blockperiods (BLOCK 0-BLOCK 6) of FIG. 3) based on radio block periods foruse by mobile stations for downlink and/or uplink radio blockcommunications. In the illustrated example, the partial timeslotassignment structure 400 is described using CSN.1 (Concrete SyntaxNotation 1). In the illustrated example, when the partial timeslotassignment structure 400 is used to make a partial assignment, it isconfigured to include either one-in-N assignment fields 502 or bitmapassignment fields 602. In use, one of the one-in-N assignment field 502or the bitmap assignment field 602 may be selected for use in assigningradio block periods based on different radio block period intervals(e.g., radio block period quantities (N)) as described above inconnection with FIG. 3. For example, when the first bit in the partialtimeslot assignment structure 400 is set to zero (0), the access network104 communicates a packet assignment message (e.g., a packet uplinkassignment message, a packet downlink assignment message, a packettimeslot reconfigure message, a packet switched (PS) handover commandmessage, etc.) having the one-in-N assignment fields 502 as shown inFIG. 5. Alternatively, when the first bit in the partial timeslotassignment structure 400 is set to one (1), the access network 104communicates a packet assignment message having the bitmap assignmentfields 602 as shown in FIG. 6.

Turning to FIG. 5, the one-in-N assignment fields 502 of a packetassignment message include a block interval field 504 and an optionalstart block field 506. In the illustrated example, the block intervalfield 504 is a 3-bit field that stores the value of the radio blockperiod quantity (N) for a one-in-N assignment. In some exampleimplementations, the start block field 506 can be dynamically enabled ordisabled.

If the start block field 506 is enabled, the value in the start blockfield 506 represents a particular radio block period position of a radioblock period sequence (e.g., the radio block period sequence 200 ofFIGS. 2 and 3) at which a first one of the radio block periods 302 a-c(FIG. 3) assigned using the one-in-N assignment is located. Otherwise,if the start block field 506 is disabled, the one-in-N radio blockperiod assignment for a target mobile station begins with the radioblock period in which the packet assignment message containing theone-in-N assignment fields 502 is completely received.

Alternatively, if the start block field 506 is disabled, the one-in-Nradio block period assignment for a target mobile station may begin atsome deterministic point in time. In some example implementations, adeterministic point in time may be the next radio block period meeting arequirement associated with a TDMA frame number of the first frame in aradio block period. For example, if the block interval field 504specifies N=3 (three radio block periods), a repeat length of 13 TDMAframes (i.e., 3 (radio block periods)×4 (TDMA frames/radio blockperiod), plus 1 idle/PTCCH frame) is required. Thus, the partialassignment starts in the next radio block period where FN mod 13=0,where FN is the TDMA frame number of the first frame in that radio blockperiod.

Turning to FIG. 6, the bitmap assignment fields 602 of a packetassignment message include a repeat length field 604 and an assignmentbitmap field 606. In the illustrated example, the repeat length field604 is a 2-bit field that indicates the radio block length of a resourceassignment bitmap and, thus, the length of the repeating pattern ofassigned blocks. The assignment bitmap field 606 is an n-bit field,where (n) represents a quantity of bits equal to the radio block lengthindicated in the repeat length field 604. For example, if the repeatlength field 604 represents 12 radio blocks (i.e., an assigned radioblock pattern repeats every 12 radio blocks), the assignment bitmapfield 606 includes n=12 bits. In such an example, each of the n=12 bitsrepresents a respective one of 12 radio blocks, and each of the n=12bits can be set to zero (0) or set to one (1). A zero (0) in one of then=12 bits indicates that resources, such as timeslots or radio blocks,in a corresponding radio block period (BLOCK 0-BLOCK 7 of FIGS. 2 and 3)are not assigned (and, thus, may not be subsequently allocated to atarget mobile station (e.g., the mobile station 102 of FIG. 1)), while aone (1) in one of the n=12 bits indicates that resources (e.g., theradio block 304 a of FIG. 3) in a corresponding radio block period(e.g., the radio block period 302 a (BLOCK 0)) are assigned (and, thus,may subsequently be allocated to the target mobile station). The patternof assigned and not assigned resources noted in the n=12 assignmentbitmap is then repeated every 12 radio blocks so that resources of thenext radio block periods are assigned (and, thus, allocatable to thetarget mobile station) in the same relative positions in each repeatingsequence of 12 radio blocks. In some example implementations, such asones in which an assignment bitmap is used, partial assignments maycomprise any pattern or sequence of assigned and non-assigned radioblock periods (e.g., patterns or sequences of any combination ofconsecutive and/or non-consecutive assigned radio block periods).Partial assignments may, thus, be permitted in instances in which themajority of radio block periods are assigned or in instances in whichthe majority of radio block periods are not assigned. In some exampleimplementations, the bitmap length may be shorter than the repeatlength, in which cases the mobile station 102 interprets block periodsfor which no corresponding bit is present in the bitmap as not assigned(or, alternatively, assigned).

The partial timeslot assignment structure 400 may be used to assignuplink resources (e.g., a PDCH) or to assign downlink resources (e.g., aPDCH) for a mobile station. For example, to assign downlink resources ina GSM/GPRS network, the access network 104 may send the one-in-Nassignment fields 502 or the bitmap assignment fields 602 to the mobilestation 102 using a PACKET DOWNLINK ASSIGNMENT message on a PacketAssociated Control Channel (PACCH) used to convey control or signalinginformation (e.g., acknowledgements and power control information,resource assignments, and/or resource requirements).

To assign uplink resources in a GSM/GPRS network, the access network 104may send the one-in-N assignment fields 502 or the bitmap assignmentfields 602 to the mobile station 102 using a PACKET UPLINK ASSIGNMENTmessage on a PACCH. In some example implementations (e.g., in two-phaseaccess establishment scenarios), the access network 104 may send thePACKET UPLINK ASSIGNMENT to the mobile station 102 on the PACCH inresponse to receiving a PACKET RESOURCE REQUEST message from the mobilestation 102. In other example implementations (e.g., in one-phase accessestablishment scenarios), the access network 104 may include the partialtimeslot assignment structure 400 in an IMMEDIATE ASSIGNMENT message tothe mobile station 102 on a Common Control Channel (CCCH) in response toreceiving a CHANNEL REQUEST message or EGPRS PACKET CHANNEL REQUESTmessage from the mobile station 102. In known techniques, part of anassignment message may indicate which timeslots (i.e., PDCHs) areassigned for uplink or downlink transmission, and may indicateadditional parameters such as an allocation mode, power controlparameters, USF values, etc. Preferably, but not necessarily, partialassignments are indicated by the combination of such known indicatorsand a partial assignment structure (e.g., the partial assignmentstructure 400) within a single message, such that the parameters ofknown techniques may be considered “valid” (and in particular,addressing parameters such as TFIs, USFs, etc.) only during certainradio block periods. Existing assignment messages may assign resourcesindefinitely (e.g., until a TBF is released by conventional means andsignaling) and a partial assignment is similarly valid while the TBF isassigned and not released. However, a partial assignment may also applyto a connection of pre-determined duration or length (e.g., which may beexpressed in terms of time or data quantity).

In some example implementations, the access network 104 may use a singleinstance of a partial assignment structure such as the partial timeslotassignment structure 400 to simultaneously indicate the radio blockperiods containing the assigned downlink and uplink resources for amobile station. When implemented in connection with GSM/GPRS systems,the access network 104 may specify the assigned radio block periodsassociated with such simultaneous downlink and uplink assignments bycommunicating only one instance of either the one-in-N assignment fields502 or the bitmap assignment fields 602 to the mobile station 102 in aPACKET TIMESLOT RECONFIGURE message on a PACCH. Alternatively oradditionally, the access network 104 may omit some or all of a partialassignment structure (e.g., the partial timeslot assignment structure400) from a subsequent assignment message when the newly assigned ormodified resources are assigned in the radio block periods aligned withthose associated with an existing TBF assignment. Such an alignment maynot necessarily imply either co-incidence or a one-to-one correspondence(or both) between assigned uplink radio block periods and assigneddownlink radio block periods. For example, when an uplink TBF isassigned where a downlink TBF is already assigned (or vice versa), theassigned resources may be aligned such that the radio block periodsduring which USFs would be sent to allocate assigned uplink resourcesare the same as the radio block periods during which downlink TBFresources may be allocated. In such a case, the access network 104 mayinclude an indication (e.g., other than a complete partial assignmentstructure) such as, for example, a USF offset field 702 of FIG. 7, todistinguish the assignment from a non-partial assignment. The mobilestation 102 may, thus, determine the partial nature (and thecorresponding applicable radio block periods) of an assignment from anassignment message that does not contain a complete or explicitindication of the assigned radio block periods.

Alternatively or additionally, the access network 104 may include apartial assignment structure in a subsequent assignment message in thecase that both the newly assigned or modified resources and resourcesassociated with an ongoing TBF are assigned in the radio block periodsindicated by the partial assignment structure. Such alignment may notnecessarily imply either co-incidence or a one-to-one correspondence (orboth) between assigned uplink radio block periods and assigned downlinkradio block periods. In such example implementations, the access network104 may include an indication in addition to or as part of a partialassignment structure to indicate that the partial assignment structureis to be used to determine the partial assignment of an ongoing TBF aswell as of a new (or explicitly modified) TBF. The mobile station 102may, thus, determine the (new or modified) partial nature (and thecorresponding applicable radio block periods) of an existing TBF from anassignment message which does not contain a complete assignment for theTBF. For example, a mobile station having an ongoing uplink TBF mayreceive a PACKET DOWNLINK ASSIGNMENT message specifying a downlink TBFand indicating a partial assignment, and the mobile station may inferfrom this information that the ongoing uplink TBF is also now a partialassignment. The mobile station may determine the assigned radio blockscorresponding to the uplink TBF based on the partial assignmentindication in the PACKET DOWNLINK ASSIGNMENT message.

In some example implementations, the access network 104 may beconfigured to use the partial timeslot assignment structure 400 toimplicitly indicate assigned uplink resources based on explicit downlinkresource assignments or vice versa. For example, the access network 104may communicate the one-in-N assignment fields 502 or the bitmapassignment fields 602 to the mobile station 102 using a PACKET DOWNLINKASSIGNMENT message on a PACCH. In turn, the mobile station 102 maydecode the explicit downlink resource assignment and be configured tointerpret a subsequent uplink resource assignment as also implicitlybeing a partial assignment, aligned with the ongoing, downlinkassignment. For example, if an explicit downlink resource assignmentincludes radio block periods 0, 4, 8, etc., the mobile station 102 mayinterpret a subsequent uplink resource assignment (which may, forexample, include a USF offset indicator equal to three (3)) as includingradio block periods 3, 7, 11, etc. In such an example, the implieduplink radio block period assignments are offset by a radio block periodinterval of three (3) from the explicit downlink radio block periodassignments. In example implementations in which a USF offset indicator(e.g., in a USF offset field 702 of FIG. 7) is not used, a detected USFvalue is handled using legacy rules (e.g., the allocated uplink radioblock occurs during the radio block period occurring immediately afterthe radio block period containing the USF value), and the partial uplinkassignment is, thus, correspondingly determined. Thus, in exampleimplementations in which assigned radio blocks are indicated implicitly(e.g., based on a previous partial assignment), the relationship betweenuplink radio block periods and downlink radio block periods iscorrespondingly determined, such that radio block periods in which USFsare sent to allocate assigned resources are the same as those in whichdownlink radio blocks may be allocated.

FIG. 7 depicts an uplink state flag (USF) offset field 702 that can becommunicated in a packet assignment message from the access networkinterface 108 to the mobile station 102. In the illustrated example, theUSF offset field 702 is used by the access network 104 to indicate thatallocated uplink radio block periods are offset from downlink radioblock periods containing USF values by a quantity of radio block periodsequal to a value in (or otherwise indicated by) the USF offset field702. For example, if the USF offset field 702 indicates a value of two(2), the mobile station 102 is allocated an uplink radio block periodwithin a block period that is offset by two radio blocks from a downlinkradio block containing a USF value corresponding to the mobile station102 as shown in FIG. 8.

Turning to FIG. 8, an example uplink and downlink radio blocktransaction is shown between the access network interface 108 and themobile station 102 based on a USF offset value corresponding to themobile station 102 in the USF offset field 702 of FIG. 7. The accessnetwork interface 108 may communicate uplink allocation indicators(e.g., USFs) in the headers of downlink radio blocks. In the illustratedexample of FIG. 8, after the access network interface 108 communicatesthe USF offset field 702 to the mobile station 102 with a USF offsetvalue of two (2), the mobile station 102 monitors downlink radio blocksfor a USF value corresponding to (e.g., identifying, associated with, orassigned to a TBF assigned to) the mobile station 102. In theillustrated example, the mobile station 102 detects a USF value 802 inthe header of the radio block transmitted in timeslot 2 of each offrames F0-F3 (i.e., during radio block period BLOCK 2). In turn, basedon the detected USF value and the USF offset value in the USF offsetfield 702 (FIG. 7), the mobile station 102 is allocated uplink radioblock 804 (i.e., an uplink resource) during the radio block periodoccurring two radio block periods after a previous uplink radio blockperiod on the timeslot with the same number as (or, in other words, thecorresponding timeslot to) the timeslot containing the USF value 802. Asshown, the USF offset value of 2 in the USF offset field 702 indicatesthat receiving the USF value 802 in the downlink radio block periodBLOCK 2 does not allocate any uplink radio block in the subsequentuplink radio block period BLOCK 3, but instead allocates an uplink radioblock in the radio block period BLOCK 4.

The illustrated example of FIG. 8 depicts the USF value 802 in a BTTIradio block configuration, in which the USF value 802 appears in a radioblock transmitted during the four frames (F0-F3). Alternatively, a USFtransmitted in BTTI configuration may allocate an uplink RTTI radioblock (e.g., using “BTTI USF mode” as defined in 3GPP TS 44.060). Theresource allocation technique of FIG. 8 may be implemented with theallocated block offset by either a quantity of BTTI radio block periodsor a number of RTTI radio block periods. Alternatively, the resourceallocation technique of FIG. 8 may be implemented using an RTTI radioblock configuration using an RTTI USF mode, in which the access networkinterface 108 locates the USF value 802 in a downlink radio blocktransmitted using two timeslots (e.g., timeslots 0 and 1 as shown inFIG. 2) of a first frame (F0) and the other two of the USF values 802 inrespective timeslots (e.g., timeslots 0 and 1) of a next frame (F1). Inthis manner, the access network 104 may allocate an RTTI radio block(e.g., the RTTI radio block 204 of FIG. 2) to the mobile station 104.This approach may be employed independent of the correspondence (ormapping) between the timeslot number(s) on which an assigned USF istransmitted or detected and the timeslot number(s) of the resultingallocated uplink radio blocks. Known methods that could be combined withthis approach include dynamic allocation (e.g., a USF in one radio blockindicates an allocation of one or more uplink radio blocks). Inaddition, this approach may be used when the uplink resources allocatedby a USF span multiple radio block periods (e.g., as may be indicated bya known USF GRANULARITY parameter). For example, a quantity of RLC/MAC(Radio Link Control/Medium Access Control) blocks to transmit on eachallocated uplink PDCH/PDCH-pair may be controlled using a USFGRANULARITY parameter characterizing an uplink TBF. As is known, if USFGRANULARITY is set to four blocks allocation, the mobile station 102 mayignore the USF on all other PDCHs/PDCH-pairs during the first threeblock periods in which the mobile station has been granted permission totransmit. As is also known, the USF corresponding to the last threeblocks of a four radio block allocation may be set to an unused valuefor each PDCH/PDCH-pair on which a mobile station has been grantedpermission to transmit.

The resource allocation technique of FIGS. 7 and 8 may be used inconnection with the one-in-N partial assignment or the bitmap partialassignment techniques described above in connection with FIGS. 4-6. Forexample, the access network 104 may send a partial assignment using oneof the one-in-N partial assignment technique or the bitmap partialassignment technique and the USF offset field 702 to the mobile station102. Subsequently, the access network 104 may communicate the USF value802 to the mobile station 102 to allocate uplink radio blocks. Forexample, a DL PACCH for conveying the USF offset field 702 may beconstrained to DL timeslots that are to be monitored in accordance withan assigned UL and/or DL TBF (e.g., a UL and/or DL TBF assigned using apartial assignment). The USF value 802 may be constrained to the sameradio block periods assigned by the partial assignment for use in DLdata transmissions. In this manner, the mobile station 102 may receivethe USF values 802 even if it is only decoding the radio blockstransmitted during radio block periods assigned to it based on a partialdownlink assignment.

FIG. 9 depicts an example downlink radio block sequence in which USFtransmissions 902 allocating resources to the mobile station 102 arealigned with downlink radio block periods 906 a-c assigned to the samemobile station 102 for receiving data from the access network 104 (i.e.,the USF transmissions 902 are transmitted in radio block periods duringwhich the mobile station 102 is required to monitor downlink radioblocks based on its downlink assignment). In the illustrated example ofFIG. 9, the downlink radio block periods 906 a-c may be assigned to themobile station 102 based on either of the one-in-N partial assignmenttechnique or the bitmap partial assignment technique described above inconnection with FIGS. 4-6. As shown, the assigned downlink radio blockperiod 906 a is separated from the next occurring assigned downlinkradio block period 906 b by non-assigned downlink radio block periods907 a-b.

In the illustrated example, the USF transmissions 902 indicate uplinkresources 904 a-b allocated to the mobile station 102. Configuring theaccess network 104 to send USFs allocating resources to the mobilestation 102 in the same downlink radio block periods 906 a-c in whichthe mobile station 102 can expect to receive data (and communicatinginformation indicating such a configuration to the mobile station 102)improves communications efficiency by allowing the mobile station 102 toenter into a low-power mode during intervening radio blocks by nothaving to decode every downlink radio block for the presence of acorresponding USF value. That is, the mobile station 102 may decoderadio blocks (e.g., the radio blocks 304 a-c of FIG. 3 or any otherradio blocks of assigned radio block periods) of only those downlinkradio block periods (e.g., the radio block periods 906 a-c) assigned toit for receiving downlink data and determine whether those downlinkradio block periods contain USF values intended for the mobile station102. Because USF values corresponding to the mobile station 102 are nottransmitted by the access network 104 in downlink radio block periodsother than the downlink radio block periods 906 a-c, the mobile station102 will not miss any USF values intended for it if it only decodes thedownlink radio block periods 906 a-c and ignores all other radio blockperiods.

The illustrated example of FIG. 9 also depicts an uplink radio blockperiod assignment (radio block periods 908 a-b) for the mobile station102 based on a USF offset value of two as described above in connectionwith the USF offset field 702 of FIG. 7. In the illustrated example ofFIG. 9, it is preferable, but not necessary, that an uplink radio blockperiod (e.g., the uplink radio block period 908 a or the uplink radioblock period 908 b) having an uplink resource (e.g., an uplink radioblock 904 a or an uplink radio block 904 b) allocated to the mobilestation 102 occurs at least at an offset of two relative to an allocateddownlink radio block period (e.g., the downlink radio block period 906 aor the downlink radio block period 906 b) so that the mobile station 102has at least a one radio block period delay for processing data or otherinformation (e.g., ACK/NACK information sent by the access network 104related to previous data sent by the mobile station 102 to the accessnetwork 104). Thus, it is preferable, but not necessary, that theassigned radio block periods are correspondingly aligned. In theillustrated example of FIG. 9, the assigned uplink radio block period908 a is separated from the next occurring assigned uplink radio blockperiod 908 b by non-assigned radio block periods 909 a-b. Also in theillustrated example of FIG. 9, uplink radio block periods 908 a-b occurtwo radio block periods after respective previous downlink radio blockperiods 906 a-b.

In some instances, when a mobile station cannot confirm whether anaccess network successfully received data (e.g., based on ACK/NACKinformation) previously communicated by the mobile station, the mobilestation re-transmits the data in an attempt to ensure that the accessnetwork successfully receives it. Because of the at least one radioblock period delay as shown in FIG. 9, the mobile station 102 of FIG. 1can decode and process any data or information (including ACK/NACKinformation at any protocol layer which may, for example, confirmwhether data previously transmitted by the mobile station 102 wassuccessfully received by the access network 104) in the most recentlyreceived downlink radio block and, thus, can generate appropriate datain response and/or select more appropriate data to transmit in thenext-occurring uplink resource(s). In this manner, the mobile station102 need only re-transmit data for which it could not confirm successfulreceipt based on ACK information and may prioritize retransmission ofdata for which it has received a negative acknowledgment or otherindication that it has not been received by the network. In systems thatdo not provide such a delay between allocated downlink radio blocks anduplink radio blocks, mobile stations may not have sufficient time toprocess most recently received ACK/NACK information to avoidunnecessarily transmitting data that such ACK/NACK information confirmsas being successfully received by an access network. In addition,allowing a delay of one or more radio block periods as shown in FIG. 9may improve the timeliness and appropriateness of transmissions(including ACK/NACK information transmitted in response to downlink datatransmitted by the network) sent by the mobile station 102.

FIG. 21 depicts an example temporary block flow (TBF) offset table 2100showing uplink state flag (USF) values 2102 and different USF offsets(e.g., offset=1 and offset=2) assigned to multiple TBFs (e.g., TBFs A,B, C, D, E, F, G, H). In some example implementations, two or more ofthe TBFs A, B, C, D, E, F, G, H may be the same TBF. For example, TBFssharing the same value but with two different offsets may be the sameTBF such that the reception of a single assigned USF value indicates anallocation in multiple radio block periods. The TBF offset table 2100shows how the use of different USF offset values may be used to assignthe same USF value on the same PDCH or timeslot to multiple TBFs toallow more users (e.g., more mobile stations) to share a single uplinktimeslot. For example, as shown in FIG. 21, five distinct USF values(more distinct values (e.g., 7 or 8) may be used in other exampleimplementations) are assigned to eight TBFs (e.g., TBFs A-H) for thesame timeslot. In particular, USF value 0 is assigned to TBF A toindicate that TBF A is allocated a radio block offset by one (1) from aradio block period in which the USF value 0 was transmitted by an accessnetwork (e.g., the access network 104 of FIG. 1). In addition, USF value0 is also assigned to a TBF E to indicate that TBF E is allocated aradio block offset by two (2) from a radio block period in which the USFvalue 0 was transmitted by an access network (e.g., the access network104 of FIG. 1). Similarly, USF values 1-4 may be assigned to other TBFsto indicate similar types of resource allocations. In this manner, USFvalues may be re-used to indicate different resource allocations todifferent TBFs or mobile stations. For example, in the illustratedexample of FIG. 21, each TBF A-H may be assigned to a respective mobilestation, and each mobile station may respond accordingly when it detectsits assigned USF value. Although FIG. 21 shows only USF offset values ofone (1) and two (2), higher offset values may be used in other exampleimplementations. Higher offset values may be advantageously used toincrease the quantity of TBFs or mobile stations that can be multiplexedfor each USF value. Preferably, but not necessarily, at least onevalue/USF-offset combination is reserved (e.g., is not assigned to anymobile station or TBF) to allow the access network 104 to avoidscheduling two different mobile stations/TBFs in the same timeslot (asshown in FIG. 22).

FIG. 22 depicts an example uplink and downlink radio block transaction2200 between the access network interface 108 of FIG. 1 and one or moremobile stations (not shown) in connection with the USF offset values ofFIG. 21. As shown in FIG. 22, when a mobile station associated with TBFC receives USF value=2 in radio block period (RBP) BLOCK 0, the mobilestation is allocated a radio block RBP BLOCK 1 based on USF value=2 andoffset=1 for TBF C as shown in the TBF offset table 2100 of FIG. 21.However, when the USF value=2 is received in radio block period (RBP)BLOCK 0 by a mobile station associated with TBF G, the mobile station isallocated a radio block in RBP BLOCK 2 based on USF value=2 and offset=2for TBF G as shown in the TBF offset table 2100. Similarly, a mobilestation associated with TBF D that receives USF=3 in RBP BLOCK 2 isallocated a radio block in RBP BLOCK 3 based on an offset=1 in the TBFoffset table 2100, while a mobile station associated with TBF H thatreceives USF=3 in RBP BLOCK 2 is allocated a radio block in RBP BLOCK 4based on an offset=2 in the TBF offset table 2100. Thus, a single USFvalue may be used to indicate allocated resources in two different RBPsfor a single TBF or two different TBFs (e.g., TBFs assigned to twodifferent mobile stations).

FIG. 10 depicts a known technique of specifying maximum radio blocktransmissions and/or receptions per radio block period, and thus, themaximum quantity of radio blocks that can be transmitted and/or receivedper radio block period for the mobile station 102. As shown in FIG. 10,known techniques allow a maximum quantity of radio blocks (e.g., 10radio blocks) to be received by mobile stations per radio block period(e.g., based on a maximum number of timeslots on which a mobile stationcan receive data per TDMA frame). The maximum quantity of allowableradio blocks may be based on the processing capabilities (e.g., aprocessing capabilities limitation) of the mobile station. For example,a slower processing mobile station will have a smaller quantity ofmaximum quantity of allowable radio blocks per radio block period, whilea faster processing mobile station will have a larger quantity ofmaximum allowable radio blocks because the faster processing mobilestation can process more received data than the slower processing mobilestation before a next occurring radio block. Some mobile communicationsstandards define a maximum quantity of allowable radio blocks based onan Rx_Sum parameter (e.g., an example Rx_Sum parameter is defined in3GPP TS 45.002 v. 9.3.0 for a maximum quantity of allowable radio blocksa single radio block period).

Mobile stations may additionally or alternatively be subject tosecondary capabilities limitations associated with other aspects of themobile stations. For example, such secondary capabilities limitationsmay include minimum switching times (i.e., minimum times required toswitch between transmit and receive modes with or without performingneighbor cell measurements). Some example industry mobile communicationstandards define minimum switching times as parameters Tra, Trb, Tta,and Ttb, which may be characterized by a multislot class included in amobile station's radio access capabilities. Some secondaryconsiderations may include a maximum quantity of transmit timeslots (aTx value) per TDMA frame, a maximum quantity of receive timeslots (an Rxvalue) per TDMA frame, and/or a maximum sum of transmit and receivetimeslots per TDMA frame. Some example industry mobile communicationstandards define such a maximum quantity of transmit timeslots (a Txvalue), a maximum quantity of receive timeslots (an Rx value), and/ormaximum sums of transmit and receive timeslots per TDMA frame, which mayall be characterized by a multislot class. These secondary capabilitieslimitations may permit a higher quantity of radio blocks to be used fortransmission and/or reception within a particular radio block periodthan is possible according to the processing capabilities of a mobilestation. Some example industry mobile communication standards (e.g.,3GPP TS 45.002 and 3GPP TS24.008, in which is described a MultislotCapability Reduction for Downlink Dual Carrier field) define quantitiesof radio blocks to be used for transmission and/or reception within aparticular radio block period based on a difference between the maximumquantity of downlink timeslots possible due to secondarycapabilities/restraints and the maximum quantity of downlink timeslotspossible due to processing, or other similar, capabilities restrictions.A device (in particular, one capable of receiving on multiple carrierssimultaneously (e.g., a device that supports a downlink dual carrierfeature)) may be constrained by its processing capabilities that limitthe quantity of radio blocks of data that it can process per radio blockperiod, such that secondary capabilities limitations (e.g., based onswitching times) are not the dominant limiting factor.

FIG. 11 depicts an example technique in accordance with the examplemethods and apparatus described herein for specifying a maximumallowable cumulative quantity of radio blocks over a multiple downlinkradio block period interval (e.g., a multiple downlink radio blockperiod interval 1102). In the illustrated example, instead of specifyinga maximum allowable quantity of radio blocks for a single radio blockperiod as shown in the known technique of FIG. 10, the example techniqueof FIG. 11 may be used to characterize the processing capabilities of amobile station over a multiple downlink radio block period interval 1102(e.g., a group of two or more consecutive radio block periods) tospecify a maximum allowable cumulative quantity of radio blocks that canbe processed by a mobile station within the time corresponding to themultiple downlink radio block period interval 1102. In the illustratedexample of FIG. 11, the mobile station 102 can receive and process amaximum allowable cumulative quantity of 20 radio blocks over twodownlink radio block periods that make up a multiple downlink radioblock period interval 1102. That is, during the occurrence of a multipledownlink radio block period interval 1102, the mobile station 102 canreceive up to 20 radio blocks of data such that the 20 radio blocks ofdata could all occur in a first radio block period forming a multipledownlink radio block period interval 1102 (or, preferably, but notnecessarily, a quantity of radio blocks of data, as limited by secondarycapabilities limitations (e.g., based on switching times, Rx values, Txvalues, etc.)), a second radio block period forming the same multipledownlink radio block period interval 1102 (or, preferably, but notnecessarily, a quantity of radio blocks of data, as limited by secondarycapabilities limitations (e.g., based on switching times)) or partiallyin the first block period and partially in the second block period. Inany case, the example technique depicted in FIG. 11 allows the accessnetwork 104 to communicate information to the mobile station 102 in aflexible manner over two radio block periods, and the mobile station 102has sufficient processing power to decode and process the 20 radioblocks of received data during the two radio block periods.

In some example implementations, the maximum quantity of allowable radioblocks per radio block period may be indicated by, for example, anindication in the RAC of the mobile station 102 that the maximumcumulative quantity of resources that the mobile station 102 is capableof receiving over a multiple downlink radio block period interval 1102is specified by a receive sum (Rx_Sum) parameter (e.g., an Rx_Sumparameter defined in 3GPP TS 45.002 v. 9.3.0 which, in known systems,corresponds to a single radio block period) multiplied by a quantity ofradio block periods in the multiple downlink radio block period interval1102. In some example implementations, a maximum allowable cumulativequantity of radio blocks may be based on a sliding window over two ormore radio block periods. For example, the maximum allowable cumulativequantity of radio blocks could be applied to all/any consecutive numberof radio block periods such that radio block periods [n+1, n+2] aresubject to a maximum radio block restriction and radio block periods[n+2, n+3] (i.e., n+2 is an overlapping radio block period) are alsosubject to the same maximum radio block restriction.

Turning to FIG. 12, the access network interface 108 can use the maximumallowable cumulative quantity of 20 radio blocks shown in FIG. 11 tosend downlink data to the mobile station 102 as shown. For example, theaccess network interface 108 can transmit 12 radio blocks of data at afirst radio block period forming a multiple downlink radio block periodinterval 1102 and zero radio blocks of data in a second radio blockperiod forming the same multiple downlink radio block period interval1102. Such a transmission technique can be advantageously used toprovide the mobile station 102 with idle time to enter low power modes,and/or to receive and process a given amount of data while consumingrelatively less power. For example, in the transmission scenario of FIG.12, the mobile station 102 may enter into a low power mode during BLOCK1, BLOCK 3, and BLOCK 5. Such low power opportunities would not beavailable using the known maximum allocated radio block configuration ofFIG. 10 when needing to transmit more than 10 radio blocks of data,because the access network interface 108 could only transfer a maximumof 10 radio blocks of data in any one radio block period so that 12total radio blocks of data would need to be transmitted over twoconsecutive radio block periods (e.g., BLOCK 0 could be used to transmit6 radio blocks of data and BLOCK 1 could be used to transmit 6 radioblocks of data) and the mobile station 102 would not be provided withany idle time since every radio block period would carry some dataneeding to be received and decoded by the mobile station 102.

In the illustrated example of FIGS. 11 and 12, maximum radio blockquantities (e.g., the maximum 20 radio blocks) are specified overgroupings of two radio block periods, each forming a separate one of themultiple downlink radio block period intervals 1102. In other exampleimplementations, such maximum radio block quantities may be specifiedover groupings of more radio block periods. In addition, to allow areceiving device (e.g., the mobile station 102) to process data receivedover a single radio block period grouping (e.g., one of the multipledownlink radio block period intervals 1102), an access network (e.g.,the access network 104) may, during one or more subsequent radio blockperiods, transmit no additional data intended for the receiving device.Since reception of data blocks may temporarily exceed the processingcapabilities of the mobile station 102, the mobile station 102 may bepermitted additional time to process some or all radio blocks, withcorrespondingly modified requirements on, for example, the maximum timebetween receipt of a radio block and the reflection of its status(received/not received) in ACK/NACK information transmitted by themobile station 102. In some example implementations, the access network104 may send zero radio blocks of data in some radio block periods (andmake the mobile station 102 aware of this in advance) by using a partialassignment (e.g., a partial assignment using the partial timeslotassignment structure 400 of FIG. 4). In some example implementations,similar techniques may be employed in connection with uplinktransmissions.

Although FIGS. 11 and 12 describe maximum radio block quantitiesspecified over groupings of two or more radio block periods based oncapabilities of the mobile station 102, in some example implementations,maximum radio block quantities may be applied in a similar manner forcommunications from the mobile station 102 to the access network 104. Insuch example implementations, the access network 104 may be constrainedbased on processing capabilities or other, secondary capabilities of theaccess network interface 108 (or other network devices). The accessnetwork 104 may inform the mobile station 102 of such constraints orcapabilities, and the mobile station 102 may use the techniquesdescribed in connection with FIGS. 11 and 12 to transmit data to theaccess network 104 based on a maximum radio block quantity of data thatthe access network 104 is able to receive over two or more radio blockperiods and/or based on other, secondary capabilities of the accessnetwork 104.

FIG. 13 depicts an example polling field 1302 transmitted by the accessnetwork interface 108 to the mobile station 102 on a downlink PDCH torequest control information and/or ACK/NACK information (e.g., requestedinformation 1304) from the mobile station 102. In legacy GSM/GPRSsystems, access networks poll mobile stations using different pollingcodes representing uplink radio block allocations to the mobile stationsand the type of information that is being requested from the mobilestations. When implemented in connection with EGPRS systems, the pollingfield 1302 may be a Combined EGPRS Supplementary/Polling (CES/P) field.The example methods and apparatus described herein for partialassignments may be used in connection with polling processes.

In some example implementations, the response to a poll is to betransmitted within a radio block period, where the radio block period isdetermined by taking into account the partial assignment of the mobilestation 102 (and, preferably, but not necessarily, the radio blockperiod in which the poll was received and, optionally, the contents ofthe polling field 1302) rather than solely based on the position of theradio block period in which the poll was received and the contents ofthe polling field 1302, as is done in known systems. For example,according to known standards, a poll may indicate an allocation to themobile station 102 (or, alternatively, that a response is to betransmitted by the mobile station 102) in a radio block period that istwo block periods after the radio block period in which the poll wasreceived at the mobile station 102. However, using the exampletechniques described herein, a poll may be used to indicate anallocation in a radio block period that is the J^(th) (e.g., second)radio block period (of radio block periods indicated by a previous andstill valid partial assignment) after the radio block period in whichthe poll is received by the mobile station 102. For example, differentpolling codes may represent different values of J. Preferably, but notnecessarily, this approach may be used when the previous and still validpartial assignment for the mobile station 102 includes one or moreuplink assignments. Alternatively, a poll may indicate an allocation ina radio block period that is valid according to either a previous andstill valid uplink assignment or a previous and still valid downlinkassignment. However, this approach may also be used when the mobilestation 102 has no valid uplink assignment, but does have a previous andstill valid downlink assignment.

In some example implementations, the access network 104 may use legacypolling codes for communication to the mobile station 102 in the pollingfield 1302, but the mobile station 102 is configured to ignore anyallocation indicated by such legacy polling codes that does not matchradio block periods previously identified by the access network 104using any one or more of the partial assignment techniques describedherein. For example, the access network 104 may communicate a partialassignment to the mobile station 102 using any of the techniquesdescribed herein. As long as such partial assignment is valid, themobile station 102 can ignore any polls from the access network 104 thatdo not specify a radio block period matching a previously indicatedpartial assignment (including the union of two or more such assignments)that is still valid. Preferably, but not necessarily, when the mobilestation 102 has a partial uplink assignment, this approach may be usedand a previous and still valid partial assignment relates to one or moreuplink assignments. Alternatively, the access network 104 may specify aradio block period that is valid according to either a previous andstill valid uplink assignment or a previous and still valid downlinkassignment. However, this approach may also be used when the mobilestation 102 has no valid uplink assignment, but does have a previous andstill valid downlink assignment.

Additionally or alternatively, the access network 104 may be configuredto communicate polling codes to the mobile station 102 via the pollingfield 1302 without such polling codes specifying any resource allocationto the mobile station 102 to be used for a response from the mobilestation 102. In some example implementations, the polling codes mayoptionally be used to indicate only a type of information that theaccess network 104 is requesting from the mobile station 102. In someexample implementations, upon receiving a polling code in the pollingfield 1302 from the access network 104, the mobile station 102interprets the receipt of the polling code as meaning that it shouldrespond to the access network 104 on a subsequent (and preferably, butnot necessarily, the next) available uplink radio block that isallocated to it by the access network using any of the assignment andresource allocation techniques described herein or already known in theart. In such example implementations, the mobile station 102 mayoptionally decode the polling code to identify the requested information1304.

FIGS. 14-18 and 23 depict example flow diagrams representative ofprocesses that may be implemented using, for example, computer readableinstructions that may be used to implement partial assignments and/orallocations of network resources to enable communications betweennetworks (e.g., the access network 104 of FIG. 1) and mobile stations(e.g., the mobile station 102 of FIGS. 1, 5-8, 12, and 13). The exampleprocesses of FIGS. 14-18 and 23 may be performed using one or moreprocessors, controllers, and/or any other suitable processing devices.For example, the example processes of FIGS. 14-18 and 23 may beimplemented using coded instructions (e.g., computer readableinstructions) stored on one or more tangible computer readable mediasuch as flash memory, read-only memory (ROM), and/or random-accessmemory (RAM). As used herein, the term tangible computer readable mediumis expressly defined to include any type of computer readable storageand to exclude propagating signals. Additionally or alternatively, theexample processes of FIGS. 14-18 and 23 may be implemented using codedinstructions (e.g., computer readable instructions) stored on one ormore non-transitory computer readable media such as flash memory,read-only memory (ROM), random-access memory (RAM), cache, or any otherstorage media in which information is stored for any duration (e.g., forextended time periods, permanently, brief instances, for temporarilybuffering, and/or for caching of the information). As used herein, theterm non-transitory computer readable medium is expressly defined toinclude any type of computer readable medium and to exclude propagatingsignals.

Alternatively, some or all of the example processes of FIGS. 14-18 and23 may be implemented using any combination(s) of application specificintegrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)),field programmable logic device(s) (FPLD(s)), discrete logic, hardware,firmware, etc. Also, some or all of the example processes of FIGS. 14-18and 23 may be implemented manually or as any combination(s) of any ofthe foregoing techniques, for example, any combination of firmware,software, discrete logic and/or hardware. Further, although the exampleprocesses of FIGS. 14-18 and 23 are described with reference to the flowdiagrams of FIGS. 14-18 and 23, other methods of implementing theprocesses of FIGS. 14-18 and 23 may be employed. For example, the orderof execution of the blocks may be changed, and/or some of the blocksdescribed may be changed, eliminated, sub-divided, or combined.Additionally, any or all of the example processes of FIGS. 14-18 and 23may be performed sequentially and/or in parallel by, for example,separate processing threads, processors, devices, discrete logic,circuits, etc.

Turning now to FIG. 14, a depicted example flow diagram representativeof computer readable instructions may be used to employ the partialassignment data structure 400 of FIG. 4 to identify assigned radio blockperiods (e.g., the radio block periods 302 a-c of FIG. 3). Initially,the mobile station 102 receives a packet assignment message (block1402). In the illustrated example, the mobile station 102 may receivethe packet assignment message from the access network 104 (FIG. 1), andthe packet assignment message may contain the one-in-N assignment fields502 or the bitmap assignment fields 602 of the partial timeslotassignment structure 400 of FIG. 4. In some instances, the packetassignment message may not contain a partial assignment, but may insteadcontain an assignment according to legacy assignment techniques. Themobile station 102 determines whether the packet assignment messagecontains a partial assignment (block 1404). If the packet assignmentcontains a partial assignment, the mobile station 102 determines whetherthe packet assignment message contains a partial assignment bitmap(block 1406). For example, a partial assignment bitmap may be in theform of the bitmap assignment fields 602 described above in connectionwith FIG. 6. In the illustrated example, the mobile station 102 maydetermine whether the packet assignment message includes a partialassignment bitmap by determining whether the first bit in the receivedpartial timeslot assignment structure 400 is set to one (1).

If the packet assignment message does not include a partial assignmentbitmap (block 1406), the packet assignment message may include aone-in-N partial assignment, and control advances to block 1408. Atblock 1408, the mobile station 102 retrieves a block interval from thepacket assignment message. For example, the mobile station 102 mayretrieve a block interval value from the block interval field 504 ofFIG. 5. The mobile station 102 determines whether the packet assignmentmessage includes a start block value (block 1410). For example, thepacket assignment message may include a start block value in the startblock field 506 of FIG. 4. If the packet assignment message includes thestart block value, the mobile station 102 retrieves the start blockvalue from the packet assignment message (block 1412).

After the mobile station 102 retrieves the start block value (block1412) or if the packet assignment message includes a partial assignmentbitmap (block 1406) or if the packet assignment message does not includea partial assignment (block 1404), control advances to block 1414. Atblock 1414, the mobile station 102 determines a next occurring assignedradio block period (e.g., one of the radio block periods 302 a-c of FIG.3). For example, if the packet assignment message includes a partialassignment but does not include a partial assignment bitmap, the mobilestation 102 may determine the next occurring assigned radio block periodbased on the block interval value retrieved at block 1408 and, ifpresent, the start block value retrieved at block 1412, as describedabove in connection with FIG. 5. If the packet assignment messageincludes a partial assignment bitmap, the mobile station 102 maydetermine the next occurring assigned radio block period based on arepeat length value stored in the repeat length field 604 and anassignment bitmap stored in the assignment bitmap field 606 as describedabove in connection with FIG. 6. Otherwise, if the packet assignmentmessage does not include a partial assignment, the mobile station 102may determine a next occurring assigned radio block period based on alegacy assignment technique. In the illustrated example, depending onthe type of packet assignment message received at block 1402 (e.g., aPACKET UPLINK ASSIGNMENT message, a PACKET DOWNLINK ASSIGNMENT message,or a PACKET TIMESLOT RECONFIGURE message), the next occurring assignedradio block period may be an uplink radio block period or a downlinkradio block period, or the next occurring assigned radio block periodmay indicate assigned uplink and downlink radio block periods at aparticular radio block period position.

The mobile station 102 then monitors (and/or processes) downlinkcommunications either in the next occurring radio block period assignedfor downlink communications, or in the next radio block period duringwhich uplink allocation indicators (e.g., the USF value 802 of FIG. 8 orthe USF values 902 of FIG. 9) may be received which allocate resourcesin an assigned radio block period for uplink communications (block1416). The mobile station 102 then determines whether a data transfer(e.g., a TBF connection) has ended (block 1418). If the data transfersession (e.g., a TBF connection) has not ended, control returns fromblock 1418 to block 1414. Otherwise, the data transfer session is ended(block 1420) by, for example, the mobile station 102 or the accessnetwork 104 and the example process of FIG. 14 ends.

FIG. 15 depicts an example flow diagram representative of computerreadable instructions that may be used to identify allocated uplinkresources based on an uplink state flag (USF) offset (e.g., a USF offsetvalue in the USF offset field 702 of FIG. 7) and received USF values(e.g., the USF values 802 of FIG. 8 or 902 of FIG. 9). Initially, themobile station 102 receives a USF flag offset value (block 1502) in, forexample, the USF offset field 702. The mobile station 102 then monitorsa subsequent downlink radio block period for a USF value correspondingto it (block 1504).

In some example implementations, at block 1504, the mobile station 102may monitor (and/or process) radio blocks during every downlink radioblock period and determine whether it contains a USF value correspondingto the mobile station 102 at block 1504. Alternatively, at block 1504,the mobile station 102 may monitor (and/or process) radio blocks onlyduring those downlink radio block periods that have been previouslyassigned to the mobile station 102 using a partial assignment fordownlink communications such as either of the partial assignmenttechniques of FIGS. 5 and 6 if these are the same radio block periods asthose in which uplink allocation indicators (e.g., USF values thatallocate resources in an assigned radio block period for uplinkcommunications) may be received. In this manner, the mobile station 102can monitor, for USF values, only during downlink radio block periods(e.g., the downlink radio block periods 906 a-c of FIG. 9) that may alsocontain data sent by the access network 104 as described above inconnection with FIG. 9, and the mobile station 102 may advantageouslyoperate in lower power modes during non-assigned radio block periods.

The mobile station 102 determines whether it has detected a USF valuecorresponding to it in the monitored downlink radio block period (block1506). If the mobile station 102 does not detect a corresponding USFvalue (block 1506), control returns to block 1504. Otherwise, if themobile station 102 does detect a corresponding USF value (block 1506),the mobile station 102 identifies a subsequent allocated uplink resource(e.g., one of the allocated uplink radio blocks 904 a-b of FIG. 9)(block 1508). For example, the mobile station 102 may identify thesubsequent allocated uplink resource based on the downlink radio blockperiod position of the USF value detected at block 1506 and the USFoffset value received at block 1502 as described above in connectionwith FIGS. 7-9.

The mobile station 102 sends data to the access network 104 in theallocated uplink resource(s) (e.g., one of the allocated uplink radioblocks 904 a-b) (block 1510). The example process of FIG. 15 then ends.Of course, the mobile station 102 may continue to monitor downlink radioblock periods and perform the operations of blocks 1504, 1506, 1508, and1510 as described above to send further data to the access network 104.

FIG. 23 depicts an example flow diagram representative of computerreadable instructions that may be used by the access network 104 to sendindications of uplink resource allocations to the mobile station 102during assigned downlink radio block periods (e.g., the downlink radioblock periods 906 a-c of FIG. 9) using the USF values 902 of FIG. 9.Initially, the access network interface 108 sends a downlink assignmentmessage to the mobile station 102 (block 2302). The downlink assignmentmessage may include a partial assignment based on either of the one-in-Npartial assignment technique or the bitmap partial assignment techniquedescribed above in connection with FIGS. 4-6, or any other radio blockperiod assignment technique. If the downlink assignment message includesa partial assignment based on either of the one-in-N partial assignmenttechnique or the bitmap partial assignment technique described above inconnection with FIGS. 4-6, at least one radio block period (e.g., thedownlink radio block period 906 a) assigned by the partial assignment isseparated from a next occurring radio block period (e.g., the downlinkradio block period 906 b) also assigned by the partial assignment by oneor more non-assigned radio block period (e.g., the downlink radio blockperiods 907 a-b of FIG. 9).

The access network interface 108 sends an uplink assignment message tothe mobile station 102 (block 2304). The uplink assignment message mayinclude a partial assignment based on either of the one-in-N partialassignment technique or the bitmap partial assignment techniquedescribed above in connection with FIGS. 4-6, or any other radio blockperiod assignment technique. If the uplink assignment message includes apartial assignment based on either of the one-in-N partial assignmenttechnique or the bitmap partial assignment technique described above inconnection with FIGS. 4-6, at least one radio block period (e.g., theuplink radio block period 908 a) assigned by the partial assignment isseparated from a next occurring radio block period (e.g., the uplinkradio block period 908 b) also assigned by the partial assignment by oneor more non-assigned radio block period (e.g., the uplink radio blockperiods 909 a-b of FIG. 9).

The access network interface 108 allocates an uplink radio block (e.g.,the uplink radio block 904 a or the uplink radio block 904 b) to themobile station 102 to occur during an assigned uplink radio block period(e.g., the uplink radio block period 908 a or the uplink radio blockperiod 908 b) (block 2306). The access network interface 108 sends a USF(e.g., the USF 902 of FIG. 9) to the mobile station 102 in an assigneddownlink radio block period (e.g., one or more of the downlink radioblock periods 906 a-c of FIG. 9) (block 2308). The example process ofFIG. 23 then ends.

FIG. 16 depicts an example flow diagram representative of computerreadable instructions that may be used to send data to the mobilestation 102 using a maximum cumulative quantity of resources allowableover multiple downlink radio block periods as described above inconnection with FIGS. 11 and 12. Initially, the access network interface108 (FIGS. 1 and 12) retrieves a maximum allowable quantity of resources(e.g., radio blocks) for a destination mobile station (e.g., the mobilestation 102) over multiple radio block periods (block 1602), such as,one of the multiple downlink radio block period intervals 1102 of FIG.11. In some example implementations, the access network interface 108may retrieve radio access capabilities (RAC) information from the mobilestation 102 or from the core network 106 indicating the maximumcumulative quantity of resources that the mobile station 102 is capableof receiving over a multiple downlink radio block period interval 1102(e.g., two or more radio block periods). For example, as described inconnection with FIGS. 11 and 12, the mobile station 102 may be capableof receiving, and thus processing, 20 radio blocks of data during twoconsecutive downlink radio block periods forming the multiple downlinkradio block period interval 1102. In some example implementations, thismay be indicated by an indication in the RAC of the mobile station 102that the maximum cumulative quantity of resources that the mobilestation 102 is capable of receiving over a multiple downlink radio blockperiod interval 1102 is specified by a receive sum (Rx_Sum) parameter(e.g., an example Rx_Sum parameter defined in 3GPP TS 45.002 v. 9.3.0which, in known systems, corresponds to a single radio block period)multiplied by a quantity of radio block periods in the multiple downlinkradio block period interval 1102.

The access network interface 108 then schedules a data transmission tothe destination mobile station 102 based on the maximum allowablequantity of resources (block 1604). For example, the access networkinterface 108 may schedule portions of data to be sent in each downlinkradio block period of a particular multiple downlink radio block periodinterval 1102 so that all schedule data portions do not exceed themaximum allowable quantity of resources during the multiple downlinkradio block period interval 1102. The access network interface 108 mayadditionally take into account restrictions that apply on a per-TDMAframe basis or per-radio block basis, which may also be determined basedon the RAC of the mobile station 102.

The access network interface 108 sends first data in a first downlinkradio block (block 1606). For example, the access network interface 108may use 12 radio blocks to send data in a downlink radio block periodBLOCK 0 as shown in FIG. 12 or use any other quantity of radio blocks.The access network interface 108 determines whether it has more data tosend to the mobile station 102 (block 1608). If the access networkinterface 108 has more data to send (block 1608), the access networkinterface 108 sends the next data in a next radio block period of thesame multiple downlink radio block period interval 1102 (block 1610) andcontrol returns to block 1608.

If the access network interface 108 does not have any more data to send(block 1608), the access network interface 108 may end the data transfer(block 1612). For example, the access network interface 108 may end aTBF. In some example implementations, the data transfer may end, whilethe TBF is not ended. The example process of FIG. 16 then ends.

FIG. 17 depicts an example flow diagram representative of computerreadable instructions that may be used to identify allocated uplinkradio blocks based on the polling request 1302 of FIG. 13 received fromthe access network interface 108. Initially, the mobile station 102receives the polling request 1302 (block 1702) and decodes a pollingcode contained therein (block 1704). In the illustrated example of FIG.17, the polling code indicates the type of information that the accessnetwork 104 is requesting from the mobile station 102. In some exampleimplementations of the example process of FIG. 17, the polling code mayalso indicate a radio block period in which the mobile station 102 is torespond to the polling request by sending the requested information 1304(FIG. 13) to the access network interface 108. In other exampleimplementations of the example process of FIG. 17, the polling code mayindicate the type of information requested from the mobile station 102but may not indicate a radio block period. In such exampleimplementations, the mobile station 102 uses a previous partialassignment to identify uplink radio block periods assigned to the mobilestation 102 and uses those identified uplink radio block periods to sendthe requested information 1304 to the access network interface 108. Theprevious partial assignment may be made using, for example, either ofthe one-in-N partial assignment technique or the bitmap partialassignment technique described above in connection with FIGS. 4-6, orany other radio block period assignment technique.

The mobile station 102 determines an assigned uplink radio block periodin which to send the requested information 1304 to the access networkinterface 108 (block 1706). As discussed above, the polling code mayexplicitly indicate the radio block period for use by the mobile station102 in sending the requested information 1304 (e.g., with reference toan existing, valid assignment), or the polling code may not have such anindication, in which case the mobile station 102 may refer to a previouspartial assignment of radio block periods made by the access network104.

The mobile station 102 sends the requested information 1304 in theassigned uplink radio block period (block 1708), and the example processof FIG. 17 ends.

FIG. 18 depicts another example flow diagram representative of computerreadable instructions that may be used to identify allocated uplinkradio blocks based on the polling request 1302 of FIG. 13 received froma network. Initially, the mobile station 102 receives the pollingrequest 1302 (block 1802) and decodes a polling code contained therein(block 1804). In the illustrated example of FIG. 18, the polling codeindicates the type of information that the access network 104 isrequesting from the mobile station 102 and also indicates an uplinkradio block period during which the mobile station 102 is expected tosend the requested information 1304 (FIG. 13) to the access networkinterface 108.

The mobile station 102 determines an uplink radio block period (block1806) based on the polling code decoded at block 1804. The mobilestation 102 determines whether the uplink radio block period is inaccordance with a radio block period indicated by a previous, and stillvalid, partial assignment (block 1808) made by, for example, the accessnetwork 104. For example, the radio block period indicated by thepolling code may or may not match a radio block period of a previous,and still valid, partial assignment made by the access network 104using, for example, either of the one-in-N partial assignment techniqueor the bitmap partial assignment technique described above in connectionwith FIGS. 4-6, or any other radio block period assignment technique.

If the uplink radio block period indicated by the polling code decodedat block 1804 does match a radio block period (e.g., an uplink radioblock period) of a previous, and still valid, partial assignment (block1808), the mobile station 102 sends the requested information 1304 inthe radio block period indicated by the decoded polling code (block1810). Otherwise, if the radio block period indicated by the pollingcode decoded at block 1804 does not match a radio block period of aprevious, and still valid, partial assignment, the mobile station 102ignores the polling request 1302 (block 1812).

After ignoring the polling request (block 1812) or after sending therequested information (block 1810), the example process of FIG. 18 ends.

Now turning to FIG. 19, an illustrated example of the mobile station 102of FIGS. 1, 5-8, 12, and 13 is shown in block diagram form. In theillustrated example, the mobile station 102 includes a processor 1902that may be used to control the overall operation of the mobile station102. The processor 1902 may be implemented using a controller, a generalpurpose processor, a digital signal processor, dedicated hardware, orany combination thereof.

The example mobile station 102 also includes a FLASH memory 1904, arandom access memory (RAM) 1906, and an expandable memory interface 1908communicatively coupled to the processor 1902. The FLASH memory 1904 canbe used to, for example, store computer readable instructions and/ordata. In some example implementations, the FLASH memory 1904 may be usedto store instructions that may be executed to cause the processor 1902to implement one or more operations associated with one or more of theexample processes of FIGS. 14-18 and 23. The RAM 1906 may be used to,for example, store data and/or instructions. The mobile station 102 isalso provided with an external data I/O interface 1910. The externaldata I/O interface 1910 may be used by a user to transfer information toand from the mobile station 102 through a wired medium.

The mobile station 102 is provided with a wireless communicationsubsystem 1912 to enable wireless communications with wireless networkssuch as mobile communication networks, cellular communications networks,wireless local area networks (WLANs), etc. To enable a user to use andinteract with or via the mobile station 102, the mobile station 102 isprovided with a speaker 1914, a microphone 1916, a display 1918, and auser input interface 1920. The display 1918 can be an LCD display, ane-paper display, etc. The user input interface 1920 could be analphanumeric keyboard and/or telephone-type keypad, a multi-directionactuator or roller wheel with dynamic button pressing capability, atouch panel, etc.

The mobile station 102 is also provided with a real-time clock (RTC)1922 to track durations of timeslots, radio blocks, or radio blockperiods and/or to implement time-based and/or date-based operations. Inthe illustrated example, the mobile station 102 is a battery-powereddevice and is, thus, provided with a battery 1924 and a batteryinterface 1926.

Turning now to FIG. 20, the example access network interface 108 ofFIGS. 1, 5-8, 12, and 13 is shown in block diagram form. The accessnetwork interface 108 a base station controller (BSC) 2002communicatively coupled to a base transceiver station (BTS) 2004. In theillustrated example, the BSC 2002 is connected to the core network 106and implements operations and processes associated with a packet controlunit (PCU) for a GSM/EDGE (Enhanced Data rates for GSM Evolution) radioaccess network (GERAN). In the illustrated example, the BTS 2004 is incommunication with the BSC 2002 and connected to an antenna tocommunicate wirelessly with mobile station such as the mobile station102 of FIGS. 1, 5-8, 12, 13, and 19.

In the illustrated example of FIG. 20, the BSC 2002 includes a processor2002 to perform the overall operations of the BSC 2002. In addition, theBSC 2002 includes a FLASH memory 2008 and a RAM 2010, both of which arecoupled to the processor 2006. The FLASH memory 2008 may be configuredto store instructions that may be executed to cause the processor 2006to implement one or more operations associated with one or more of theexample processes of FIGS. 14-18 and 23. The RAM 2010 may be used tostore data to be exchanged between a core network (e.g., the corenetwork 106 of FIG. 6) and mobile stations (e.g., the mobile station102). In addition, the RAM 2010 may be used to store radio accesscapabilities (RACs) of mobile stations including, for example, a maximumallowable cumulative quantity of timeslots that can be processed by amobile station within the time corresponding to a multiple downlinkradio block period interval 1102 of FIG. 11.

To communicate with a core network (e.g., the core network 106), the BSC2002 is provided with a network communication interface 2012. In theillustrated example, the network communication interface 2012 isconfigured to communicate with a GSM/GERAN core network. In otherexample implementations, the network communication interface 2012 may beconfigured to communicate with any other type of network including a3GPP network, a code division multiple access (CDMA) network, etc.

Although certain methods, apparatus, and articles of manufacture havebeen described herein, the scope of coverage of this patent is notlimited thereto. To the contrary, this patent covers all methods,apparatus, and articles of manufacture fairly falling within the scopeof the appended claims either literally or under the doctrine ofequivalents.

1. A method to receive resource assignments at a mobile station,comprising: receiving an assignment message from a network; identifyingradio block periods assigned to the mobile station, at least one of theassigned radio block periods being separated from a next occurring oneof the assigned radio block periods by at least one non-assigned radioblock period; and processing downlink transmissions from the networkbased on the assigned radio block periods.
 2. A method as defined inclaim 1, wherein the processing of the downlink transmissions from thenetwork based on the assigned radio block periods comprises decoding anuplink allocation indicator, and further comprising transmitting anuplink data block during an uplink radio block period in response to theuplink allocation indicator, wherein the uplink radio block periodoccurs during one of the assigned radio block periods.
 3. A method asdefined in claim 1, wherein the processing of the downlink transmissionsfrom the network based on the assigned radio block periods comprisesignoring an uplink allocation indicator that does not allocate an uplinkradio block during one of the assigned radio block periods.
 4. A methodas defined in claim 1, wherein the processing of the downlinktransmissions from the network based on the assigned radio block periodscomprises ignoring downlink data received during a radio block periodthat is not assigned to the mobile station.
 5. A method as defined inclaim 1, wherein the assignment message specifies a quantity ofnon-assigned radio block periods separating the at least one of theassigned radio block periods from the next occurring one of the assignedradio block periods, the at least one non-assigned radio block periodforming part of the quantity of non-assigned radio block periods.
 6. Amethod as defined in claim 5, wherein the assignment message specifies aradio block period position at which a first one of the assigned radioblock periods is located.
 7. A method as defined in claim 1, wherein theassignment message comprises an assignment bitmap representative of apattern of assigned radio block periods and non-assigned radio blockperiods.
 8. (canceled)
 9. A method as defined in claim 7, whereinreceiving the assignment message comprises receiving a repeat lengthspecifying a quantity of radio block periods after which the pattern ofthe assigned and non-assigned radio block periods specified in theassignment bitmap repeats.
 10. (canceled)
 11. A method as defined inclaim 1 further comprising, prior to receiving the assignment messagefrom the network, sending capabilities to the network indicative ofresource assignment types compatible with the mobile station.
 12. Anapparatus to receive resource assignments at a mobile station,comprising: a processor configured to: receive an assignment messagefrom a network; identify radio block periods assigned to the mobilestation, at least one of the assigned radio block periods separated froma next occurring one of the assigned radio block periods by at least onenon-assigned radio block period; and process downlink transmissions fromthe network based on the assigned radio block periods.
 13. An apparatusas defined in claim 12, wherein the processor is configured to processthe downlink transmissions from the network based on the assigned radioblock periods by decoding an uplink allocation indicator, and whereinthe processor is configured to transmit an uplink data block during anuplink radio block period in response to the uplink allocationindicator, the uplink radio block period occurring during one of theassigned radio block periods.
 14. An apparatus as defined in claim 12,wherein the processor is configured to process the downlinktransmissions from the network based on the assigned radio block periodsby ignoring an uplink allocation indicator that does not allocate anuplink radio block during one of the assigned radio block periods. 15.An apparatus as defined in claim 12, wherein the processor is configuredto process the downlink transmissions from the network based on theassigned radio block periods by ignoring downlink data received during aradio block period that is not assigned to the mobile station.
 16. Anapparatus as defined in claim 12, wherein the assignment messagespecifies a quantity of non-assigned radio block periods separating theat least one of the assigned radio block periods from the next occurringone of the assigned radio block periods, the at least one non-assignedradio block period forming part of the quantity of non-assigned radioblock periods.
 17. An apparatus as defined in claim 16, wherein theassignment message specifies a radio block period position at which afirst one of the assigned radio block periods is located.
 18. Anapparatus as defined in claim 12, wherein the assignment messagecomprises an assignment bitmap representative of a pattern of assignedradio block periods and non-assigned radio block periods.
 19. (canceled)20. An apparatus as defined in claim 18, wherein the processor isconfigured to receive a repeat length in the assignment message, therepeat length specifying a quantity of radio block periods after whichthe pattern of the assigned and non-assigned radio block periodsspecified in the assignment bitmap repeats.
 21. (canceled) 22.(canceled)
 23. A network device to send resource assignments to a mobilestation, comprising: a processor configured to: send an assignmentmessage indicative of radio block periods assigned to the mobilestation, at least one of the assigned radio block periods separated froma next occurring one of the assigned radio block periods by at least onenon-assigned radio block period; and sending downlink transmissions tothe mobile station based on the assigned radio block periods.
 24. Anetwork device as defined in claim 23, wherein the assignment messagespecifies a quantity of non-assigned radio block periods separating theat least one of the assigned radio block periods from the next occurringone of the assigned radio block periods, the at least one non-assignedradio block period forming part of the quantity of non-assigned radioblock periods.
 25. A network device as defined in claim 24, wherein theassignment message specifies a radio block period position at which afirst one of the assigned radio block periods is located.
 26. A networkdevice as defined in claim 23, wherein the assignment message comprisesan assignment bitmap representative of a pattern of assigned radio blockperiods and non-assigned radio block periods.
 27. (canceled)
 28. Anetwork device as defined in claim 26, wherein the assignment messagefurther comprises a repeat length specifying a quantity of radio blockperiods after which the pattern of the assigned and non-assigned radioblock periods specified in the assignment bitmap repeats.
 29. (canceled)30. (canceled)